We are currently using the https://www.npmjs.com/package/@composio/openclaw-plugin with some patches from this PR (https://github.com/ComposioHQ/openclaw-composio-plugin/pull/2) to allow us to use the plugin with the "Composio Platform" instead of just "For You". We see that the OpenClaw plugin has now been deprecated and have some questions about the path forward. The plugin appears to have advantages over the CLI or MCP setup: 1. Automatically injects into the system prompt instructions about composio as well as errors if they occur (https://github.com/ComposioHQ/openclaw-composio-plugin/blob/master/src/prompt.ts) 2. Exposes native LLM tools vs. relying on SKILLS or other best effort mechanisms for the LLM to know how to use Composio. https://github.com/ComposioHQ/openclaw-composio-plugin/blob/master/src/tools.ts#L83-L128 Although the plugin documentation points to recommending using the CLI instead of the plugin, on the composio.dev website in the top navigation the "Products -> OpenClaw" menu item points to a page https://composio.dev/claw that describes using MCP, not the CLI - contradicting the migration guidance on openclaw-composio-plugin (https://github.com/ComposioHQ/openclaw-composio-plugin#composio-plugin-for-openclaw). So the question I have is: Which path is preferred/recommended by Composio for using Composio Platform with OpenClaw - CLI or MCP or ? Note OpenClaw lacks native MCP client support so MCP is routed through the CLI via mcporter https://github.com/steipete/mcporter. So for our use case of: - Managed OpenClaw instances for our customers - Using Composio Platform (NOT For You) What is the Composio preferred path? CLI and SKILLS feel like a step back from the plugin. As the openclaw plugin docs state: "We're excited to announce our Universal CLI, optimized for use with OpenClaw. It outperformed this plugin on internal benchmarks, and we recommend migrating to it." - what is the setup used that outperformed the plugin?

hi, i am doing the same thing. how do u solve the multi-tetancy problem? i think you don't want your users to set up composio every time right?

We solved the multi tenancy issue with applying the changes from the fork PR on top of HEAD of OC plugin. https://github.com/ComposioHQ/openclaw-composio-plugin/pull/2

I just used mcp porter with open claw and it worked fine. Though restrictive on the base plan, but works. You can use that way. Much easier to setup.